This problem may arise when a transaction is initially posted using a payment method which uses transaction aggregation (e.g. cash to be banked) and is subsequently changed to a payment method which is processed separately (e.g. petty cash). This may be due to a member incorrectly posting the transaction or a change of mind in regards as to how the funds are to be treated.

 

Ordinarily, posting a receipt or payment which uses aggregation automatically creates a task to deposit/EFT the funds. The transaction finishes its immediate workflow in the pending state, and does not change to 'processed' until the aggregation activity is completed. If the payment method is subsequently modified to a non-aggregated type, the transaction is removed from the list of receipts/payments which can be processed in an aggregation, but does not create a new workflow; hence, the transaction remains in grey and ContactsLaw treats it as unprocessed.